This is the preview version of the Wisconsin State Legislature site.
Please see http://docs.legis.wisconsin.gov for the production version.
1. That the department is denying the request in whole or in part.
2. The reason for the denial.
3. For a person who believes that he or she is authorized under s. 153.50 (4), Stats., the procedures for appealing the denial under s. 19.37 (1), Stats.
(3)Access to patient-identifiable data. In accordance with s. 153.50, Stats., only the following persons or entities may have access to patient-identifiable data maintained by the department:
(a) A health care provider or the agent of a health care provider to ensure the accuracy of the information in the department database.
(b) An agent of the department responsible for collecting and maintaining data under this chapter and who is responsible for the patient-identifiable data in the department in order to safely store the data and ensure the accuracy of the information in the department’s database.
(c) The department for any of the following purposes:
1. Epidemiological investigation purposes specified in writing.
2. Eliminating the need to maintain duplicative databases where the requesting department agent has statutory authority to collect patient-identifiable data as defined in s. 153.50 (1) (b), Stats.
(d) Other entities that have a signed, notarized written agreement with the department, in accordance with the following conditions:
1. The entity has a statutory requirement for obtaining patient-identifiable data for any of the following:
a. Epidemiological investigation purposes.
b. Eliminating the need to maintain duplicative databases, under s. 153.50 (4) (a), Stats.
2. The department may review and approve specific requests by the entity for patient-identifiable data to fulfill the entity’s statutory requirement. The entity’s request shall include all of the following:
a. Written statutory evidence that the entity is entitled to have access to patient-identifiable data.
b. Written statutory evidence requiring the entity to uphold the patient confidentiality provisions specified in this section or stricter patient confidentiality provisions than those specified in this section. If these statutory requirements do not exist, the department shall require the entity to sign and notarize a written data use agreement to uphold the patient confidentiality provisions in this section.
Note: Examples of other entities include the U.S. Centers for Disease Control and cancer registries in other states.
(e) Of information submitted by health care providers that are not hospitals or ambulatory surgery centers, patient-identifiable data that contain a patient’s date of birth may be released to an entity specified under s. 153.50 (4) (a), Stats., upon request and a demonstrated need for the date of birth.
(f) Notwithstanding sub. (2) and pars. (a) to (e), no employer may request the release of or access to patient-identifiable data of an employee of the employer.
(g) An entity specified under s. 153.50 (4), Stats., having access to data elements considered patient-identifiable may not rerelease these data elements.
(4)Data elements considered patient-identifiable.
(a) For information submitted by hospitals and ambulatory surgery centers, all of the following data elements from the uniform patient billing form that identify a patient shall be considered confidential, except as stated in sub. (3):
1. Patient medical record or chart number.
2. Patient control or account number.
3. Patient date of birth.
4. Patient’s employment status and occurrence and place of an auto or other accident.
5. Patient’s school name, if applicable.
6. Patient’s race.
7. Patient’s ethnicity.
8. Patient’s city of residence.
9. Date of patient’s first symptom of current illness, injury or pregnancy.
10. Dates of services provided to patient.
11. Hospitalization dates related to current services provided to patient.
12. Dates patient is unable to work in current occupation.
13. Date of patient admission.
14. Date of patient discharge.
15. Date of patient’s principal procedure.
16. Encrypted case identifier.
17. Insured’s policy number.
18. Insured’s date of birth.
19. Insured’s identification number.
20. Insured’s gender.
21. Medical assistance resubmission code.
22. Medical assistance prior authorization number.
23. Patient’s employer’s name.
(b) For information submitted by health care providers who are not hospitals or ambulatory surgery centers, patient-identifiable data means all of the following elements:
1. Data elements specified in par. (a) 1. to 3., 13. to 16., 21. and 22.
2. Whether the patient’s condition is related to employment, and the occurrence and place of an auto accident or other accident.
3. Date of first symptom of current illness, of current injury or of current pregnancy.
4. First date of patient’s same or similar illness, if any.
5. Dates that the patient has been unable to work in his or her current occupation.
6. Dates of receipt by patient of medical service.
7. The patient’s city, town or village.
(5)Additional methods for ensuring confidentiality of data.
(a) In this subsection, “small number” means any number that is not large enough to be statistically significant, as determined by the department.
(b) Requests for customized data from the physician office data collection including data elements other than those available in public use files require the approval of the independent review board, except in cases where the custom request has been previously authorized in administrative rule or in policies approved by the independent review board.
(c) To ensure that the identity of patients is protected when information generated by the department is released, the department shall do all of the following:
1. Aggregate any data element category containing small numbers that would allow identification of an individual patient using procedures developed by the department and approved by the board. The procedures shall follow commonly accepted statistical methodology.
2. Mask data through any of the following techniques:
a. Combining raw data elements.
b. Recoding data from individual values to category values.
Note: Typical techniques for recoding data from individual values to category values include replacing individual ages with 5-year age groups.
c. Removing raw data elements.
d. Combining years of data to assure that breakdowns of information adequately protect against identification.
e. Using averages based on combined years of data.
History: Cr. Register, December, 2000, No. 540, eff. 1-1-01.
DHS 120.31Data dissemination.
(1)Definitions. In this section:
(a) “Calculated variable” means a data element that is computed or derived from an original data item or derived using another data source.
(b) “Release raw patient data” means to show, lend or give the raw patient data, or any subset thereof, to another person.
(2)Independent review board.
(a) The department and the board shall work with the independent review board created under s. 153.67, Stats., to establish policies and procedures applicable to processing requests for the release of physician office visit custom databases and custom analyses compiled by the department under this section. The IRB shall review any request under s. 153.45 (1) (c), Stats., for data elements other than those available for public use data files under s. 153.45 (1) (b), Stats. Unless the IRB approves a data request or unless IRB approval is not required under the rules, the department may not release the data elements.
Note: Section 153.67, Stats., was repealed by 2005 Wis. Act 228.
(b) Calculated variables added to the public use physician office databases do not require approval by the IRB before the department releases them.
(c) The independent review board shall establish acceptable custom requests for physician office data or analyses that will not require repeated re-authorizations by the IRB.
(d) The independent review board shall meet as often as necessary to review policies and requests for custom data or custom analyses of the physician office data.
(e) Notwithstanding s. 15.01 (1r), Stats., the independent review board may promulgate only those rules that are first reviewed and approved by the board on health care information.
(3)Release of data.
(a) The department may release health care provider-specific data to health care providers to whom the information relates. The department may not release any health care information prior to its review, verification and comment upon by those submitting the data in accordance with procedures described under subch. III.
(b) The department shall provide to other entities the data necessary to fulfill their statutory mandates for epidemiological purposes or to minimize the duplicate collection of similar data elements.
(c) The department may release health care provider-specific data found in hospital and freestanding ambulatory surgery center databases to requesters when data review, verification and comment procedures have been followed under s. DHS 120.11 (4).
(d) Before rereleasing any raw patient data element to subsequent users under this section, initial data purchasers shall receive written department approval for the initial purchaser’s rerelease of data. Each initial purchaser request shall be submitted to the department in writing and shall contain all of the following information:
1. The nature of the proposed rerelease.
2. The person and, if applicable, the entity the person is associated with to whom the data is proposed to be released.
3. A statement from the initial purchaser that evidences all of the following:
a. The initial purchaser’s understanding that the individual data elements cannot be rereleased until the initial purchaser receives written authorization to do so from the department.
b. The initial purchaser’s agreement to distribute the department’s confidentiality and data use agreement to subsequent users of the data.
1. Upon receipt of an initial purchaser’s request to rerelease any raw data element to subsequent users containing all of the information in par. (d), the department shall review the request and determine whether to permit the rerelease. Prior to departmental approval of the rerelease, the department must have also received a signed and notarized data use agreement form from the subsequent user. If the department approves the rerelease, the department shall send a letter authorizing rerelease to the requesting initial purchaser. The department shall also send a copy of the letter to the proposed subsequent user.
Loading...
Loading...
Published under s. 35.93, Stats. Updated on the first day of each month. Entire code is always current. The Register date on each page is the date the chapter was last published.